home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Diamond Collection
/
The Diamond Collection (Software Vault)(Digital Impact).ISO
/
cdr37
/
isr100a.zip
/
ISERVER.DOC
< prev
next >
Wrap
Text File
|
1995-02-25
|
18KB
|
401 lines
▀ █▀▀ █▀▀ █▀█ █ █ █▀▀ █▀█
█ ▀▀█ █▀ █▀▄ █ █ █▀ █▀▄ I n t e r n e t S e r v e r R e l a y
▀ ▀▀▀ ▀▀▀ ▀ ▀ ▀ ▀▀▀ ▀ ▀
Copyright Mulitboard Communications Centre, 1995
All rights reserved.
WHAT DOES THIS PROGRAM DO?
══════════════════════════════════════════════════════════════════════─────
This program imports and exports netmail into your BBS's message
base, in a way that is compatible with netmail, but to the user
it appears as internet mail. It also provides many internet
commands and functions.
WHAT DO I NEED TO SET THIS PROGRAM UP?
══════════════════════════════════════════════════════════════════════─────
In order to use this program you will need:
1) Your system to use fidonet style *.MSG files for netmail
2) A BBS that uses the JAM message format (other formats to come soon)
3) About 10 minutes to set it up
Setup method:
1) Create a message base on your BBS. For RemoteAccess, it should
be an Internet style area, JAM type.
2) Make the modifications as needed to the ISERVER.CFG file.
3) Put ISERVER.EXE in your RUNBBS.BAT file, after receiving netmail
and after the user logs off (or optionally during an event)
4) You're done.
The easiest way to setup this system is by editing the ISERVER.CFG
file to match your setup. You can refer to this appendix for more
information about a particular option if required.
WHAT CAN'T I DO UNTIL I REGISTER?
══════════════════════════════════════════════════════════════════════─────
Nothing. The only limits that are imposed, are that you can only
have a maxium of 5 RESPOND entries, and 5 RESTRICTS until registered.
It will also remove the unregistered notice, and 2 second delay.
Please register, a lot of effort went into developing the program,
and the price is quite reasonable.
CONFIGURATION COMMANDS (Explanations and examples)
══════════════════════════════════════════════════════════════════════─────
Quick note, where addresses have no points, do not specify the
point zero. For example, 1:2401/305 should not be entered as
1:2401/305.0, or it may not be processed correctly.
PROCESS - These are the addresses that iSERVER should
process for internet mail. If you have more
than one domain setup, you can enter multiple
addresses. (Maximum 10 addresses)
Example: PROCESS 1:2401/305.999
NETMAIL - This is the path to the *.MSG netmail
messages that come into and leave your
system from.
Example: NETMAIL e:\fd\mail
UPDATE - These are files you would like created after
netmail has been edited, created or deleted.
They are semaphore files used to inform other
tasks to rescan the netmail folders.
(Maximum of 10 update files)
Example: UPDATE e:\fd\FDRESCAN.NOW
XADDRESS - Not normally needed, but it allows you to
readdress an outgoing message. If the
message is addressed to the first address,
it will be readdressed to the second address.
It is mainly used for rerouting messages
from one gateway to another. (Maximum of
30 xaddresses)
Example: XADDRESS 1:1/31 1:2235/10.999
PROCESS - These are automated process requests. They
can be very powerful for responding to
messages, much like an automated full internet
server. If a message is addressed to the
first parameter, it will send the file listed
as the second parameter. Optionally, if
the second parameter begins with an asterisk
"*", it will execute the second parameter.
It will create a REQUEST file with the message
information, and read back a RESPONSE text
file, and post it if it exists. Also, a third
parameter can be added that will replace the
subject line of the returning message (if any).
Example: RESPOND HELP e:\fd\iserver\HELP.TXT
RESPOND RUNME *e:\fd\iserver\RUN.BAT
IGNORE - Messages addressed to 'ignored' names will
remain in the netmail folder as if iSERVER
never even saw them. It is good for leaving
requests upto other programs, for example:
ALLFIX, etc.. Also, if you wish your
personal mail to be leave in your netmail
folder, you can place your name in an ignore.
(Maximum 30 ignores)
Example: IGNORE allfix
IGNORE pete rocca
USERS - This is for specifying the user list for
users on your system. By using this function
iSERVER will automatically return undeliverable
messages due to 'user unknown'. This is a great
feature as messages sent to users that don't
exist will be returned, rather than sit in
your internet area, never able to be read.
(Maximum 4000 users, for systems with more
than 4000 users, please contact me at
support@mcc.uti.com for information about a
customized copy)
The second parameter specifies the type of
user listing, either RA2 for RemoteAccess 2.x
style BBS, or ASCII for a straight ASCII list
of names. The RA2 parameter checks both the
users name and alias for validity.
The third parameter is the path to the user
base for RA2, or the filename of the ASCII
text file. (Use one method only)
Example: USERS RA2 e:\ra\msgbase
or: USERS ASCII e:\fd\userlist.txt
UUCP_ADDRESS - This is the address of your gateway. If you
are using the standard Zone 1 gate, then it
would be 1:1/31, otherwise place your private
gate address here.
Example: UUCP_ADDRESS 1:2235/10.999
SITE_ADDRESS - This is the fido-style address that internet
netmail will be addressed to.
Example: SITE_ADDRESS 1:2401/305.999
SITE_NAME - This is the name of your BBS's internet site.
If you are using the fidonet gateway, then it
will be something like: p305.n2401.z1
depending on your regular netmail address.
Example: SITE_NAME mcc.uti.com
or: SITE_NAME p305.n2401.f1
SITE_BASE - This is the path to the message base you will
be using to import/export messages from.
Currently the only supported format is JAM.
The first paramater is the base type, and
the second is the path to the base.
Example: SITE_BASE JAM e:\ra\jam\EMAIL
SITE_SERVERNAME - Here you can customize what who you want to
have listed on the 'from' for automated
responsed. The normal might be 'server' or
'main-daemon'. This is just for cosmetics.
Example: SITE_SERVERNAME server
or: SITE_SERVERNAME mail-daemon
LOG - This is just the path and filename of the
log you would like created.
Example: LOG e:\ra\ISERVER.LOG
RESTRICT - This is one of the most powerful features
of iSERVER that will allow you to setup
subscription levels, or simply restrict
access to certain functions if your gateway
is long distance, or does not accept certain
types of functions.
The first parameter is the name of the
function you wish to restrict. Any outgoing
messages that have any of these names or
partial matches of these names in the 'to'
address or the first word in the subject line,
they will be considered to be restricted.
Optionally (if using RemoteAccess 2.x), you
can place a flag value (from A1 to D8) and
if the user posting the message has that
flag, they will be able to override this
restriction. (Maximum 50 restricts)
Example: RESTRICT SUBSC A2
RESTRICT LISTSERV A2
RESTRICT FTP
ALLOW_UUENCODED - By default, UUENCODED files are bounced
when attempting to be exported, however
you can override this for certain users,
users with certain flags (RA 2.x), or for
all users, using one of the following 3
methods. (Maximum 50 entries)
Example: ALLOW_UUENCODED pete rocca
ALLOW_UUENCODED A2
ALLOW_UUENCODED
REGISTER - This is the function to enter your registration
information into. The first parameter is the
serial number, and the second is the reg number.
Please register, it is very inexpensive.
Example: REGISTER 00000 0000000000000000
One of the other nice features of iSERVER is the ability to
create handles/alias's that look like customized internet names.
(RA 2.x only) This is completely optional, and somewhat seperate
from the regular functions of iSERVER. What is allows is for users
to enter an alias, and it checks it for duplicates, and also that
it conforms to standards you set, then updates the user's alias
record. You would then setup your JAM base as an alias base, and
when messages were posted, they would be from the user's alias.
Incoming messages addressed to either the users full name or their
alias would be detected during a new mail scan still. This allows
you to have user names like "admin@youraddress.com", rather than
"Pete.Rocca@youraddress.com", it's a nice touch to make your internet
system look more professional.
The following options apply to this aspect.
MAX_HANDLE_LENGTH - This is the maximum length of a name the
user can enter for thier own handle.
Example: MAX_HANDLE_LENGTH 40
MIN_HANDLE_LENGTH - This is the minimum length of a name the
user can enter for thier own handle.
Example: MIN_HANDLE_LENGTH 5
SET_HANDLE_FLAG - You can have iSERVER mark in the user
record once they have selected a valid
name. This is good for having an autoexec
menu to run the userid part of the program
if they do not have the flag set.
Example: SET_HANDLE_FLAG A1
BAD_HANDLE - These are parts of words you do not want
the user to be able to enter as their
handle. Dedicated functions, obseen language
and other personal preferences may be entered
here. (Maximum of 50 entries)
Example: BAD_HANDLE ftp
BAD_HANDLE root
BAD_HANDLE serv
COMMAND LINE PARAMETERS
══════════════════════════════════════════════════════════════════════─────
Typing ISERVER /? will bring up a list of command line options.
Normally, just running ISERVER.EXE is sufficient, but there are
other options available.
Import/export mail parameters
/PROCESS Standard behaviour (default)
/FORCE Ignore last scanning markers
/NOMARK Do not update high scan marks
/NOSCAN Do not scan for outgoing mail
/NOTOSS Do not toss incoming mail
/NOMGR Do not process requests/bounce unknown
Online programs and parameters
/USERID droppath Userid creation (if flag not toggled)
/USERID droppath /FORCE Userid creation (always)
The later two options are to run the userid (handle creation) part
of the program. The /FORCE overrides if the user has the already
set the SET_HANDLE_FLAG flag.
Examples: ISERVER.EXE /USERID c:\ra\node1 /FORCE
ISERVER.EXE /USERID c:\ra
ISERVER.EXE /USERID c:\ra\node2
LICENSE AND DISCLAIMER
══════════════════════════════════════════════════════════════════════─────
"iSERVER" (also known as "ISR") is NOT free. It is being marketed
under the "try before you buy" or shareware concept. You are entitled
to use ISR for a period up to forty-five (45) days, after which you
MUST register or stop using the program.
Registration entitles you to use ISR as well as any future versions
of this program that may or may not be released, subject to any addi-
tional licensing conditions which may be attached.
Registration will also allow you to you the full ability of ISERVER
as well as remove the unregistered notice. It will also help to con-
tinue to develop this program. (not to mention maintain the legality
of this agreement)
By running any of the executable programs included, you agree that
Pete Rocca, Multiboard Communications Centre nor any affiliates of
the above mentioned are responsible for any damage ever experienced,
however so created. If you cannot agree to this, then your privilege
to use any of these programs is revoked and it becomes illegal for
you to execute any programs included with this documentation.
You may freely copy and distribute the shareware version of ISR as
long as its original archived contents are not modified in any way.
You may NOT distribute any registration keys without the express
written consent of Pete Rocca of Multiboard Communications Centre.
You may not use a registration number that is not licensed from
Multiboard Communications Centre directly to you.
It is illegal to edit, alter, hack, reverse engineer and / or modify
any components of the ISR archive in any manner.
If dispute of any issues on legal grounds said above, then governing
law of Ontario, Canada will rule.
SUPPORT
══════════════════════════════════════════════════════════════════════─────
If you have any questions or comments, you can netmail me at FidoNet
address 1:2401/305 (CM,VFC,V32,V42). You can also send your mail to
"support@mcc.uti.com" or "pete.rocca@mcc.uti.com". In addition, the
newest MCC software is available via Internet FTP or Email.
FTP: ftp.mcs.com (/mcsnet.users/bwolf)
ACKNOWLEDGMENTS
══════════════════════════════════════════════════════════════════════─────
This program has been tested on MS-DOS 3.3 through 6.22, DESQview
2.40 through 2.63, DESQview/X 1.2 and 2.0, Windows 3.1 to 4.0 beta,
WindowsNT 3.x, OS/2 2.0 through OS/2 2.99 beta, and Novell DOS 7.0.
Other operating environments should work fine, but they have not
been fully tested. Requires at least DOS 3.3 and SHARE.EXE loaded.
DESQview, Copyrighted by Quarterdeck Software; MS-DOS, MS-Windows,
Copyrighted by Microsoft Corporation; OS/2, Copyright International
Business Machines Corp., Thanks to the public domain swapping utils
that required very little in the way of tweaking, by Thomas Wagner.
ISERVER/ISR are copyrighted products by Multiboard Communications
Centre and Pete Rocca.
Remember, please register, it's cheap!
Pete Rocca
Multiboard Communications Centre